1·The idea behind defense in depth is simple: Never rely on just one security method.
深度防御 背后的理念很简单：永远不要仅依赖于一种安全方法。
2·This key exchange security method duplicates an existing one. Either modify it, or cancel this dialog.
此密钥交换安全措施与现有的重复。请更改它，或取消此对话框。
3·The list is used to match the security method supported by the server and employed during subsequent system calls under this mount point.
这个列表用于匹配服务器支持的安全方法。 此外，随后在该装载点下发生系统调用时也用到该列表。
4·The first method is USES traditional the security method - rigid body limit zero-method, obtains the safety coefficient can satisfy the standard request.
第一种方法是采用传统的安全系数法-刚体极限平衡法，求得的安全系数能满足规范要求。
5·Because the devices which use lightweight IP protocol has limited resource, import the correlation security method will inevitably bring the influence to resource consumption.
由于轻量级IP设备的资源有限，引入相关的安全措施将不可避免地增加资源消耗。
6·Ben also talked about advanced web security requirements like method level authorization, JSR-250 for defining method security metadata, Spring security method metadata, and domain access control.
Ben还谈到了一些高级web安全需求，例如方法层的授权、定义方法安全元数据的JSR - 250规格、Spring Security方法元数据以及领域的访问控制等。
7·In this section we see how to define security roles and configure method permissions.
在此部分，我们将了解如何定义安全角色和配置方法权限。
8·To improve security, it's often wise to use more than one method of protection (also called "defense in depth").
要提高安全性，明智的做法是使用多种保护方法(也称为“深度防御”)。
9·You may prefer another method, depending on your security requirements and personal preferences.
您可能更喜欢其他方法，具体的使用取决于安全需求和个人爱好。
10·You configure EJB authentication and authorization by defining security roles in the deployment descriptor under which each method executes.
EJB 的身份验证和授权配置方法为：在部署描述符中定义安全角色，每个方法将依据部署描述符执行。